Enhancement on Substrate Node Template#8473
Conversation
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
…ubstrate-node-template Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
kianenigma
left a comment
There was a problem hiding this comment.
Looks overall good to me.
Co-authored-by: Kian Paimani <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
|
thanks @kianenigma for the review. Addressed all of your concerns, and about docker script I will deal with it in a separate issue. |
Signed-off-by: Jimmy Chu <[email protected]>
The node template here should works with latest Substrate, even though these features may not have been released in crate.io Signed-off-by: Jimmy Chu <[email protected]>
…strate to published packages Signed-off-by: Jimmy Chu <[email protected]>
apopiak
left a comment
There was a problem hiding this comment.
awesome that you're documenting the release process!
| P.S: This step can be automated if we update `node-template-release` package in | ||
| `.maintain/node-template-release`. |
There was a problem hiding this comment.
It is. But given there are 626 issues in Substrate repo already, I don't want to add another one that is kind of low priority.
There was a problem hiding this comment.
I don't think it makes sense not to create issues and have things in code, but 🤷
Co-authored-by: Alexander Popiak <[email protected]>
Co-authored-by: Alexander Popiak <[email protected]>
Co-authored-by: Alexander Popiak <[email protected]>
Co-authored-by: Alexander Popiak <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
|
@apopiak thanks for the review 🙏 |
Signed-off-by: Jimmy Chu <[email protected]>
s3krit
left a comment
There was a problem hiding this comment.
Awesome to see we're documenting this more. I'll need to look into this a lot more to think about how we can better improve the automation for releasing node-template in the future, but in the meantime this is a really good change. Glad to see it's being documented :)
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
Signed-off-by: Jimmy Chu <[email protected]>
| [*] | ||
| indent_style=space | ||
| indent_size=2 | ||
| tab_width=2 |
There was a problem hiding this comment.
did we want to commit this file?
* master: (84 commits) Duplicate logging to stdout (#8495) Fix sync restart (#8497) client: fix justifications migration (#8489) helper macro to create storage types on the fly (#8456) Make `BlockImport` and `Verifier` async (#8472) Get rid of `test-helpers` feature in sc-consensus-babe (#8486) Enhancement on Substrate Node Template (#8473) Add Social Network (#8065) Prepare UI tests for Rust 1.51 & new CI image (#8474) Benchmarking pallet-example (#8301) Use pathbuf for remote externalities (#8480) Bring back the on_finalize weight of staking. (#8463) Implement `fungible::*` for Balances (#8454) make types within `generate_solution_type` macro explicit (#8447) [pallet-staking] Refund unused weight for `payout_stakers` (#8458) Use `async_trait` in sc-consensus-slots (#8461) Repot frame_support::traits; introduce some new currency stuff (#8435) Fix &mut self -> &self in add_known_address (#8468) Add NetworkService::add_known_address (#8467) Fix companion check (#8464) ...
Co-authored-by: Kian Paimani <[email protected]> Co-authored-by: Alexander Popiak <[email protected]>
3.0.0spec_versionin runtime is set to 100node-template-release.shscript is directly using the path passed in instead of forcing to use a relative path.